feat: add Geddes Docker image for permanent Postgres+PostgREST deploy… #10
+152
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ment - geddes/Dockerfile: extends postgis/postgis image with PostgREST v13.0.6 binary baked in so it survives container restarts automatically - geddes/entrypoint.sh: custom entrypoint that starts Postgres in background, waits for it to be ready, then starts PostgREST in foreground - geddes/postgrest.conf: PostgREST configuration (secrets can be overridden at runtime via PGRST_* Kubernetes Secrets env-vars) - geddes/README.md: step-by-step build, push, and Rancher deploy instructions Problem solved: previously PostgREST was installed manually with nohup inside the running container. Every container restart wiped the installation causing the 502 Bad Gateway error seen in the Azure Function logs since Feb 2026.
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ment
Problem solved: previously PostgREST was installed manually with nohup inside the running container. Every container restart wiped the installation causing the 502 Bad Gateway error seen in the Azure Function logs since Feb 2026.